Backup Failure Alarm

System/Sub-System

MiVoice Business: Software

Description

This alarm indicates a database backup failure.

Alarm Status

Major

Possible Cause	Corrective Action
Database Audit has detected a database corruption	Collect the SOS report from the Server Manager (Administration > View Logs > Collect log files & diagnostic data) (for all platforms except Container-based MiVoice Business (cMiVB)). For Container-based MiVoice Business (cMiVB), you can collect the log files from Solution Manager > Log Files. Perform a system restore from your last known backup. If restore is successful, the alarm is cleared. If the issue persists, contact Mitel Product Support for further investigation into cause.
The Backup process was unable to stop the embedded voicemail application	Run the BUSY command: BUSY 1 4 27 BUSY 1 4 28 NOTE: If the port is in use after issuing the command, use the "Force" option to make sure that the port is in the manbusy state. Run the RTS command: RTS 1 4 27 RTS 1 4 28 Perform backup. If the issue persists, Run iPVM_Stop and iPVM_Start on the RTC shell to restart the application. Once the command is complete, attempt a manual backup. Note: this causes an interruption in voicemail services.
Insufficient disk space or file system corruption.	Provide the SOS report from the Server Manager (Administration > View Logs > Collect log files & diagnostic data) and any output from the RTC shell during the backup, and contact Mitel product support.

Possible Cause

Corrective Action

Database Audit has detected a database corruption

Collect the SOS report from the Server Manager (Administration > View Logs > Collect log files & diagnostic data) (for all platforms except Container-based MiVoice Business (cMiVB)). For Container-based MiVoice Business (cMiVB), you can collect the log files from Solution Manager > Log Files.
Perform a system restore from your last known backup. If restore is successful, the alarm is cleared.
If the issue persists, contact Mitel Product Support for further investigation into cause.

The Backup process was unable to stop the embedded voicemail application

Run the BUSY command:
- BUSY 1 4 27
- BUSY 1 4 28
NOTE: If the port is in use after issuing the command, use the "Force" option to make sure that the port is in the manbusy state.

Run the RTS command:
- RTS 1 4 27
- RTS 1 4 28

Perform backup.
If the issue persists, Run iPVM_Stop and iPVM_Start on the RTC shell to restart the application. Once the command is complete, attempt a manual backup. Note: this causes an interruption in voicemail services.

Insufficient disk space or file system corruption.

Provide the SOS report from the Server Manager (Administration > View Logs > Collect log files & diagnostic data) and any output from the RTC shell during the backup, and contact Mitel product support.